BERT, Group 50

Use Case UC3: Make Room Bookings

Revision History: current version v2, v1

Primary Actor: Employee

Stakeholders and interests:

Employee: Wants to be able to make a room booking for a given date/time period, subject to the room's availability. Wants to make a booking as a recurring event, if he/she so desires. Wants the booking to be recorded accurately and persistently.

Management: Wants employees to make their own room bookings and for booking information to be recorded accureately and persistently. Wants to be able to find out statistics on room bookings for management purposes.

Preconditions:

1. The employee has been successfully logged in to the Room Booking Subsystem.
2. The employee has the option to be redirected to Use Case UC2: View Room Bookings.
3. The room booking information is available for interrogation and modification.

Success Guarantee (Post conditions):

1. Room is recorded as booked to the employee for the specified date/time period and stored persistently.

Main Success Scenario (or Basic Flow):

1. Employee indicates they want to book a room.
2. Employee indicates the date/time(s) they want to book the room on.
3. Employee indicates the room they want to book.
4. Employee indicates they are ready for System to book the room.
5. System presents confirmation query to Employee.
6. Employee confirms booking request.
7. System records booking in persistent storage.
8. System confirms booking made.
9. System returns Employee to start of Use Case.

Actor repeats steps 1-6 until indicates done.

Extensions (or Alternative Flows):

1.a Employee wants to book a room on behalf of another staff member.

1. Employee indicates who the booking is for.
2. Use Case Resumes at Main Success Scenario step 2.

1.b Receptionist wants to book a room on behalf of an external person.

1. Receptionist indicates the booking is for an external person.
2. Receptionist advises the external person's details.
3. Use Case Resumes at Main Success Scenario step 2.

2a.System does not recognise date as valid value

1. System signals error.
2. Employee re-enters date information.

2b.Employee indicates that the booking is to be a recurring booking.

1. Employee indicates the start date for the recurring booking.
2. Employee indicates the basis of the booking (daily, monthly, weekly).
3. Employee indicates the quantity (eg 4 recurring bookings).
4. Use Case Resumes at Main Success Scenario step 3.

3a. System does not recognise the room number as a valid value.

1. System signals error.
2. Use Case resumes at Main Success Scenario step 3.

6a. Employee does not wish to confirm

1. Use Case Restarts at Main Success Scenario 1.

7a. System cannot record booking in persistent storage.

1. System signals error.

7b. Employee has attempted to book a room that is already booked.

1. System signals error.
2. System does not record the room on persistent storage.
3. Use Case restarts at Main Success Scenario 1.

Special Requirements:

-

Technology and Data Variations List:

n/a

Frequency of Occurrence:

Occurrence on an ad-hoc basis.

Open Issues:

-